Background: After upgrading to SP2 for our ReportServer boxes, we began noticing discrepancies with our reports that were exported to XML (using the "Microsoft.ReportingServices.XmlRendering.dll") that were not present in SP1. A discrepancy of particular consequence was the insertion of a new XML namespace in the root element: xmlns: p1="http://www.w3.org/2001/XMLSchema-instance" ^ (added a space before "p1"to avoid an emoticon) Now, it would be one thing is something actually used that "p1" prefix later in the XML, but that is not that case! The only thing that uses that "p1" namespace is an attribute that was automatically inserted at the root element level (p1: schemaLocation="..."), which also seems unimportant. Nonetheless, this has caused us unexpected XPath query issuesaswe were not acknowledging the new namespace in our .NET code. Questions: 1. Was this done for a reason, such as complying with new W3C standards? 2. As this is a breaking change for XPaths without a proper NamespaceManager, was this difference noted in any release documentation or white papers? 3. Is there any way to configure RS2005 SP2 such that unused namespacessuch as this one are not inserted upon XmlRender? Please let me know. Thank you! Sincerely, James Greene

Hello, We may insert XML data through .Net application into the database via the usage of stored procedure. The whole program has been illustrated in the best way in this link. You may visit it... http://www.visiontechno.net/studymats/xmlinsertion.html